Certificate Templates

During initial provisioning, the certificate templates in the primary Active Directory forestClosed (the forest in which Keyfactor Command is installed) will be imported automatically by the Keyfactor Command configuration wizard. Templates for additional forests can be imported in a number of ways:

  • For Microsoft CAs domain-joined to forests in a two-way trust with the primary forest, you can use the Import Templates option at any time.
  • For Microsoft CAs domain-joined to forests in a one-way trust with the primary forest or to a forest having no trust with the primary forest, you can use the Import Templates option after you have configured a CAClosed record for at least one Microsoft CA in the non-primary forest and enabled the Use Explicit Credentials option with credentials for the non-primary forest.
  • For EJBCA CAs, you can use the Import Templates option after you have configured a CA record for at least one EJBCA CA.
  • Templates that are associated with certificates that have been requested from a Microsoft CA in a forest other than the primary forest will appear in the templates grid as those certificates are synchronized to Keyfactor Command if you configure CA synchronization for the CA even if you don't use the import option.
  • There's an automated process to import templates once every hour, on the hour. Templates are imported for Microsoft CAs in the primary forest, Microsoft CAs in any forests in a two-way trust with the primary forest, and any CAs that can be reached using the credentials configured in the CA record (the Use Explicit Credentials option for Microsoft CAs or the client certificate for EJBCA CAs). The automated templateClosed import only runs for CAs for which there is an active CA synchronization job configured. This automated sync is only enabled if the Sync Templates option on the Service tab of the Configuration Wizard is selected during installation (see Service Tab in the Keyfactor Command Server Installation Guide).

You will need to import templates if you add a new template or change the name or key sizeClosed of a template after it has been imported into Keyfactor Command and don't want to wait for the automated import process or have not configured the automated process (see Importing Certificate Templates).

Certificate templates need to be configured to support PFXClosed and CSRClosed enrollmentClosed (see Configuring Template Options).

Note:  When EJBCA templates are imported, they are named using a naming scheme of:
  • Short Name: <end entity profile name>_<certificate profile name>
  • Display Name: <end entity profile name> (<certificate profile name>)

Only certificate profiles configured as available in a given end entity profile will be imported as templates associated with the given end entity profile name.

Figure 212: Certificate Templates

Tip:  Click the help icon () next to the Certificate Templates page title to open the embedded web copy of the Keyfactor Command Documentation Suite to this section.

You can also find the help icon at the top of the page next to the Log Out button. From here you can choose to open either the Keyfactor Command Documentation Suite at the home page or the Keyfactor API Endpoint Utility.